Skip to content

master: Update pkg/testutils/release/cockroach_releases.yaml#167505

Merged
trunk-io[bot] merged 1 commit into
cockroachdb:masterfrom
cockroach-teamcity:crdb-releases-yaml-update-master
Apr 9, 2026
Merged

master: Update pkg/testutils/release/cockroach_releases.yaml#167505
trunk-io[bot] merged 1 commit into
cockroachdb:masterfrom
cockroach-teamcity:crdb-releases-yaml-update-master

Conversation

@cockroach-teamcity
Copy link
Copy Markdown
Member

Update pkg/testutils/release/cockroach_releases.yaml with recent values.

Epic: None
Release note: None
Release justification: test-only updates

@cockroach-teamcity cockroach-teamcity force-pushed the crdb-releases-yaml-update-master branch from 169c65a to 184815c Compare April 4, 2026 00:36
@trunk-io
Copy link
Copy Markdown
Contributor

trunk-io Bot commented Apr 4, 2026

😎 Merged successfully - details.

@cockroach-teamcity
Copy link
Copy Markdown
Member Author

This change is Reviewable

@cockroach-teamcity cockroach-teamcity force-pushed the crdb-releases-yaml-update-master branch 3 times, most recently from a646173 to 6bcd962 Compare April 8, 2026 00:40
Copy link
Copy Markdown
Contributor

@celiala celiala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't remember if we're clear to bump predecessor yet from 26.1 to 26.2

let's hold on this until I can verify the pkg/clusterversion/ runbooks.

Update pkg/testutils/release/cockroach_releases.yaml with recent values.

Epic: None
Release note: None
Release justification: test-only updates
@cockroach-teamcity cockroach-teamcity force-pushed the crdb-releases-yaml-update-master branch from 6bcd962 to 0e210c5 Compare April 9, 2026 00:34
@rail
Copy link
Copy Markdown
Member

rail commented Apr 9, 2026

@celiala can you review this one?

predecessor: "26.1"
"26.3":
predecessor: "26.1"
predecessor: "26.2"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't remember if we can do this update yet (it depends on where we are in the M.x tasks)

lemme take a look in a bit

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After digging into the code: this update is safe to do at any time, regardless of where we are in the M.x cycle.

Why: predecessorSeries() in pkg/testutils/release/releases.go already skips unreleased series (those with empty Latest) when walking the predecessor chain. So setting predecessor: "26.2" now — even though 26.2 has no release yet — produces identical runtime behavior to predecessor: "26.1". The code would just skip 26.2 and fall through to 26.1 either way.

There's even an explicit test case for this: "skips unreleased predecessor" in releases_test.go.

The M.1 runbook currently directs the operator to use series-2 (instead of series-1) as a temporary measure, saying it will be corrected in M.3. That guidance is unnecessary — series-1 is always safe. We'll update the runbook in a follow-up PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

runbook update: #168049

@trunk-io trunk-io Bot merged commit c2a8c77 into cockroachdb:master Apr 9, 2026
44 of 45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants